Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae94437a4fac415187f435681fc5ff3b3541594948dde74bb8335c6d4b330663

Tx prefix hash: ad6d138635fff4ba86c9406519a8fdaa513c3c6e1204e2894f10bf055bb3db9b
Tx public key: 12dbe5c4cf07e4b7cc228df941d279fb94ab8699e33f78b4cb82a19d0ac8e5bd
Timestamp: 1723525398 Timestamp [UCT]: 2024-08-13 05:03:18 Age [y:d:h:m:s]: 00:289:11:29:02
Block: 1086782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206821 RingCT/type: yes/0
Extra: 0112dbe5c4cf07e4b7cc228df941d279fb94ab8699e33f78b4cb82a19d0ac8e5bd021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b65a7d1485411f82f8ababc169df2b5ff26e000cc696b9c986556021f145fad0 0.600000000000 1561381 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": 1086792, "vin": [ { "gen": { "height": 1086782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b65a7d1485411f82f8ababc169df2b5ff26e000cc696b9c986556021f145fad0" } } ], "extra": [ 1, 18, 219, 229, 196, 207, 7, 228, 183, 204, 34, 141, 249, 65, 210, 121, 251, 148, 171, 134, 153, 227, 63, 120, 180, 203, 130, 161, 157, 10, 200, 229, 189, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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