Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14e4f3de38730784291359b30605b71eb3d054d6f7364033a061df1add714dd6

Tx prefix hash: db51c779f22ffee5dceb7a4cbafafab656712f90fdc451dab67b2c8b520c5926
Tx public key: de0f28fb7c919044c89e68e25f0ae58f581f681ba8d0cf1b9c3ce5ffe042e95b
Timestamp: 1749867684 Timestamp [UCT]: 2025-06-14 02:21:24 Age [y:d:h:m:s]: 00:160:16:05:16
Block: 1304532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112596 RingCT/type: yes/0
Extra: 01de0f28fb7c919044c89e68e25f0ae58f581f681ba8d0cf1b9c3ce5ffe042e95b02110000000dbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 617707929fc039a0a9412e2d9ff1a5ddab7f4ac4dbff90a1235c3880865d9c50 0.600000000000 1792123 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": 1304542, "vin": [ { "gen": { "height": 1304532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "617707929fc039a0a9412e2d9ff1a5ddab7f4ac4dbff90a1235c3880865d9c50" } } ], "extra": [ 1, 222, 15, 40, 251, 124, 145, 144, 68, 200, 158, 104, 226, 95, 10, 229, 143, 88, 31, 104, 27, 168, 208, 207, 27, 156, 60, 229, 255, 224, 66, 233, 91, 2, 17, 0, 0, 0, 13, 191, 81, 178, 162, 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