Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4b6192460740cf2e3637fafa141e36d5dedcef70872a46b114e44358268cf92

Tx prefix hash: d3a659bc09a3bfc73c7c910f38c4977ab36e4432b7e66e8bba0937d9e9b24259
Tx public key: c8c40ec86a5d3691df14f3b9817ebffe45e2e2354800ea1bcb620c1c313d97a8
Timestamp: 1753785591 Timestamp [UCT]: 2025-07-29 10:39:51 Age [y:d:h:m:s]: 00:071:18:10:35
Block: 1335878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50068 RingCT/type: yes/0
Extra: 01c8c40ec86a5d3691df14f3b9817ebffe45e2e2354800ea1bcb620c1c313d97a8021100000009ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b05392cbf4514b5798723a5a46cc07a5be4c6d50652ea7ba21697a0839b4e12 0.600000000000 1823679 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": 1335888, "vin": [ { "gen": { "height": 1335878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b05392cbf4514b5798723a5a46cc07a5be4c6d50652ea7ba21697a0839b4e12" } } ], "extra": [ 1, 200, 196, 14, 200, 106, 93, 54, 145, 223, 20, 243, 185, 129, 126, 191, 254, 69, 226, 226, 53, 72, 0, 234, 27, 203, 98, 12, 28, 49, 61, 151, 168, 2, 17, 0, 0, 0, 9, 239, 34, 20, 133, 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