Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfea1fc14dc79c65f0ce7a92df1ea16957b062b657a06364444048c0a603b64b

Tx prefix hash: 4f7021bf32a900f390f7a8c28b4a987d7524faa438d5583a0c46bc6e10e8bab5
Tx public key: caa21ef815633166e86e3c2ca2f99a8936c9054e8b11e37d897737d214b95a6a
Timestamp: 1751102934 Timestamp [UCT]: 2025-06-28 09:28:54 Age [y:d:h:m:s]: 00:193:02:21:27
Block: 1314434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136157 RingCT/type: yes/0
Extra: 01caa21ef815633166e86e3c2ca2f99a8936c9054e8b11e37d897737d214b95a6a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36c6ca106ba49f5a85e1c398c7c281bb6451efb55d0d7eac31b991d2f0008712 0.600000000000 1802081 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": 1314444, "vin": [ { "gen": { "height": 1314434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36c6ca106ba49f5a85e1c398c7c281bb6451efb55d0d7eac31b991d2f0008712" } } ], "extra": [ 1, 202, 162, 30, 248, 21, 99, 49, 102, 232, 110, 60, 44, 162, 249, 154, 137, 54, 201, 5, 78, 139, 17, 227, 125, 137, 119, 55, 210, 20, 185, 90, 106, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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