Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a14caeb069037b7d1dbdcb2375fcae76b84188b2a3eac3994f40a25f04e30f21

Tx prefix hash: 546e156a79aae9fd9e1dbcf5eb2888eb959d56a09063c5ea6a4dd46049789485
Tx public key: ed4881abc3eaac043d0739cc0b79164216fb1bbbf48f3013a304ff01e6e09673
Timestamp: 1736467218 Timestamp [UCT]: 2025-01-10 00:00:18 Age [y:d:h:m:s]: 00:291:23:31:39
Block: 1193944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206168 RingCT/type: yes/0
Extra: 01ed4881abc3eaac043d0739cc0b79164216fb1bbbf48f3013a304ff01e6e0967302110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84a3edbffb0f015eb47b0ee5e61cbad03362d2801b4dc1fce74f33a4e6c6c289 0.600000000000 1680509 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": 1193954, "vin": [ { "gen": { "height": 1193944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84a3edbffb0f015eb47b0ee5e61cbad03362d2801b4dc1fce74f33a4e6c6c289" } } ], "extra": [ 1, 237, 72, 129, 171, 195, 234, 172, 4, 61, 7, 57, 204, 11, 121, 22, 66, 22, 251, 27, 187, 244, 143, 48, 19, 163, 4, 255, 1, 230, 224, 150, 115, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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