Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6140045d713d9841c4e0a2e6a0b41887b61829bbe14f4bb45ce25372fe8e1e9a

Tx prefix hash: fd92632f2cb601b71c79aae7c118c27bab46338c05f0e55de60a850227b6b57f
Tx public key: 4a0f7e81140423fd594df1fd97f139c939c4c20de3666e23562947552b602104
Timestamp: 1756408544 Timestamp [UCT]: 2025-08-28 19:15:44 Age [y:d:h:m:s]: 00:070:02:59:50
Block: 1356476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50029 RingCT/type: yes/0
Extra: 014a0f7e81140423fd594df1fd97f139c939c4c20de3666e23562947552b6021040211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1a6d4a0a0e726743d7dad6034ad70b354408f0fe2a9c7ab06370260e312f605 0.600000000000 1844485 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": 1356486, "vin": [ { "gen": { "height": 1356476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1a6d4a0a0e726743d7dad6034ad70b354408f0fe2a9c7ab06370260e312f605" } } ], "extra": [ 1, 74, 15, 126, 129, 20, 4, 35, 253, 89, 77, 241, 253, 151, 241, 57, 201, 57, 196, 194, 13, 227, 102, 110, 35, 86, 41, 71, 85, 43, 96, 33, 4, 2, 17, 0, 0, 0, 2, 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