Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdbee61684f054a67c3fc5720f53b1eb96cc5b0e63c6fbc963027224ea5b8838

Tx prefix hash: 7819d76b4540cd5f680dc4c31e90bcbc233636458efa285b57cbf166f8e0d3a7
Tx public key: 4d0b2808623321ab048dbebdb82d6b17abea02fb1e28e49fef6837e4b048f579
Timestamp: 1761681205 Timestamp [UCT]: 2025-10-28 19:53:25 Age [y:d:h:m:s]: 00:011:23:45:55
Block: 1400005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8578 RingCT/type: yes/0
Extra: 014d0b2808623321ab048dbebdb82d6b17abea02fb1e28e49fef6837e4b048f579021100000006a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71aa316a5f03f48b7d2209ee1e4fa18df147b8fd24bbd467701b0accaf09fe7a 0.600000000000 1888312 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": 1400015, "vin": [ { "gen": { "height": 1400005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71aa316a5f03f48b7d2209ee1e4fa18df147b8fd24bbd467701b0accaf09fe7a" } } ], "extra": [ 1, 77, 11, 40, 8, 98, 51, 33, 171, 4, 141, 190, 189, 184, 45, 107, 23, 171, 234, 2, 251, 30, 40, 228, 159, 239, 104, 55, 228, 176, 72, 245, 121, 2, 17, 0, 0, 0, 6, 161, 29, 186, 152, 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