Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98554fe72b0f339e68f2a8656d2380bcc494d3be92ad582c70cdefac3331a8de

Tx prefix hash: b323027cc6d8fbfa0d63759d1c9319699eb0a3d12a0c037731efa9b45efb2981
Tx public key: 0b85cf1628bbdd6a60046ee7e6207b45bd58f6b6dba181ed1e09d84b3d5a5d53
Timestamp: 1746031814 Timestamp [UCT]: 2025-04-30 16:50:14 Age [y:d:h:m:s]: 00:273:23:45:14
Block: 1272842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193461 RingCT/type: yes/0
Extra: 010b85cf1628bbdd6a60046ee7e6207b45bd58f6b6dba181ed1e09d84b3d5a5d53021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aff61caecb4cada86337ba10a9d8bc73fb90f2bf094cac0e35593c05d318ca44 0.600000000000 1760117 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": 1272852, "vin": [ { "gen": { "height": 1272842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aff61caecb4cada86337ba10a9d8bc73fb90f2bf094cac0e35593c05d318ca44" } } ], "extra": [ 1, 11, 133, 207, 22, 40, 187, 221, 106, 96, 4, 110, 231, 230, 32, 123, 69, 189, 88, 246, 182, 219, 161, 129, 237, 30, 9, 216, 75, 61, 90, 93, 83, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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