Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1896cbe035937fb3ddcb8203c9487dbc64ebe5b089a7943a04b229e91da30849

Tx prefix hash: 35671e48f6d6cf339d848a1c3491717e53fdce07edb855d9b73468e9e951dc03
Tx public key: 6c2f5792d158d20811a2d8a95ee21f79cdcb628648d8ad1c03494a36cad7b74c
Timestamp: 1761687185 Timestamp [UCT]: 2025-10-28 21:33:05 Age [y:d:h:m:s]: 00:068:22:44:46
Block: 1400053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49373 RingCT/type: yes/0
Extra: 016c2f5792d158d20811a2d8a95ee21f79cdcb628648d8ad1c03494a36cad7b74c0211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a8b48b31e6a82b672b8d34c4231b4f236a088059321a274045ce7d5b2fdd1e7 0.600000000000 1888360 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": 1400063, "vin": [ { "gen": { "height": 1400053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a8b48b31e6a82b672b8d34c4231b4f236a088059321a274045ce7d5b2fdd1e7" } } ], "extra": [ 1, 108, 47, 87, 146, 209, 88, 210, 8, 17, 162, 216, 169, 94, 226, 31, 121, 205, 203, 98, 134, 72, 216, 173, 28, 3, 73, 74, 54, 202, 215, 183, 76, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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