Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c2056590730e6c43b69dd2f4d65ab7f9499c7266ed85145ddfd359be8e48f17

Tx prefix hash: dbc8d865cbbb4e14942e53654677c1c8f9a5fe32c606d7254b677b6e03af82f5
Tx public key: ac3f7d6b921f02a40fd0815223ccd5d52480dfc0e20134d5e1543c443e0fcc8f
Timestamp: 1761637111 Timestamp [UCT]: 2025-10-28 07:38:31 Age [y:d:h:m:s]: 00:056:18:44:27
Block: 1399642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40627 RingCT/type: yes/0
Extra: 01ac3f7d6b921f02a40fd0815223ccd5d52480dfc0e20134d5e1543c443e0fcc8f021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a714dbff3f8e734d488c1ede0f188bdd775ade21088364b662289aa201b23e5b 0.600000000000 1887947 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": 1399652, "vin": [ { "gen": { "height": 1399642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a714dbff3f8e734d488c1ede0f188bdd775ade21088364b662289aa201b23e5b" } } ], "extra": [ 1, 172, 63, 125, 107, 146, 31, 2, 164, 15, 208, 129, 82, 35, 204, 213, 213, 36, 128, 223, 192, 226, 1, 52, 213, 225, 84, 60, 68, 62, 15, 204, 143, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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