Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d827383fd5f3fe9091b07068c498b8bc76ff84c8bbc971b5b7d137b3eb2d6a62

Tx prefix hash: b7a23cc441d7c4015878563c365a60b60cbb83b1a61f18f4f38453af5e8ccb22
Tx public key: dd944e7a196bbf788dafe33e3f96818c15bf474552753aa1640c2f07d49a4cf5
Timestamp: 1761222773 Timestamp [UCT]: 2025-10-23 12:32:53 Age [y:d:h:m:s]: 00:099:07:17:41
Block: 1396207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70906 RingCT/type: yes/0
Extra: 01dd944e7a196bbf788dafe33e3f96818c15bf474552753aa1640c2f07d49a4cf5021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef17460ea7ae4285b53470073ff2ea13fe0110103d2f4942d92cde8605c693b5 0.600000000000 1884492 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1396217, "vin": [ { "gen": { "height": 1396207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef17460ea7ae4285b53470073ff2ea13fe0110103d2f4942d92cde8605c693b5" } } ], "extra": [ 1, 221, 148, 78, 122, 25, 107, 191, 120, 141, 175, 227, 62, 63, 150, 129, 140, 21, 191, 71, 69, 82, 117, 58, 161, 100, 12, 47, 7, 212, 154, 76, 245, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8