Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef8419edd67e9e5256c99abee6f6f2892277c2a7dfff5282db32f23c61713bdf

Tx prefix hash: d302af37233ba42e384490c22a0958b03d97d9060a962ab6fd6a74b0234dd02d
Tx public key: 0e4e45319a6a0729dfcbf58373b5d9f9278b766291dc2ba6ea9d7d4b943d014e
Timestamp: 1760616237 Timestamp [UCT]: 2025-10-16 12:03:57 Age [y:d:h:m:s]: 00:082:11:32:46
Block: 1391171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59054 RingCT/type: yes/0
Extra: 010e4e45319a6a0729dfcbf58373b5d9f9278b766291dc2ba6ea9d7d4b943d014e0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25fba4170be3d2c449e7b5b124b335098f439085c3bf73936d20f2a0798b60d2 0.600000000000 1879418 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": 1391181, "vin": [ { "gen": { "height": 1391171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25fba4170be3d2c449e7b5b124b335098f439085c3bf73936d20f2a0798b60d2" } } ], "extra": [ 1, 14, 78, 69, 49, 154, 106, 7, 41, 223, 203, 245, 131, 115, 181, 217, 249, 39, 139, 118, 98, 145, 220, 43, 166, 234, 157, 125, 75, 148, 61, 1, 78, 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