Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9e1ed92d332985fc681dde4e9c1b379f4def9610408ef6da4871c05ea11cec8

Tx prefix hash: 04ffccbfd8cfdb0a73c01abdecba7fd863f2d274f51e14de4563d85a81ee02e4
Tx public key: 10fcf4b9ea770eb68d9f1854d6b3c1ce41d307aa4f76f89530ced42230279c0a
Timestamp: 1749924259 Timestamp [UCT]: 2025-06-14 18:04:19 Age [y:d:h:m:s]: 00:157:21:49:56
Block: 1305006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110617 RingCT/type: yes/0
Extra: 0110fcf4b9ea770eb68d9f1854d6b3c1ce41d307aa4f76f89530ced42230279c0a02110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9bd6518fc1f9cacab85c363af62b3d76689694f1b25851cadb8f8baea90c571 0.600000000000 1792603 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": 1305016, "vin": [ { "gen": { "height": 1305006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9bd6518fc1f9cacab85c363af62b3d76689694f1b25851cadb8f8baea90c571" } } ], "extra": [ 1, 16, 252, 244, 185, 234, 119, 14, 182, 141, 159, 24, 84, 214, 179, 193, 206, 65, 211, 7, 170, 79, 118, 248, 149, 48, 206, 212, 34, 48, 39, 156, 10, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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