Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 544fa37f2de580f3d64b003eebd36e951d5fabe8e74ecf729a8fd82b33ce390c

Tx prefix hash: 3eec9100079953b3fcce8c89e2f1b4c40a3724054a3a81053e40a828bed989f6
Tx public key: 2c72a4d662af50ba33a4dac9c25c6a354d3a07c6fd0df71b828bcd9f05732990
Timestamp: 1756519529 Timestamp [UCT]: 2025-08-30 02:05:29 Age [y:d:h:m:s]: 00:131:11:31:24
Block: 1357370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93996 RingCT/type: yes/0
Extra: 012c72a4d662af50ba33a4dac9c25c6a354d3a07c6fd0df71b828bcd9f05732990021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef1c3b660100fd542ff98ce5fa131c81fbd3f7c023dc6e6d5f7eb39c6dca3e15 0.600000000000 1845379 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": 1357380, "vin": [ { "gen": { "height": 1357370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef1c3b660100fd542ff98ce5fa131c81fbd3f7c023dc6e6d5f7eb39c6dca3e15" } } ], "extra": [ 1, 44, 114, 164, 214, 98, 175, 80, 186, 51, 164, 218, 201, 194, 92, 106, 53, 77, 58, 7, 198, 253, 13, 247, 27, 130, 139, 205, 159, 5, 115, 41, 144, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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