Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 462defac269e8e0f07ee0a1a0e4282e3ca709e85ef640fffd5eb9195f6b7d4ec

Tx prefix hash: c22a8495f99ae9061a4e96843e6e70b8517218ab9682398d719f82791843783b
Tx public key: e029ed3c65f8ab89f934e0a0a5aa7669d17fec0afa68761687471cdfa9aeae9d
Timestamp: 1762584020 Timestamp [UCT]: 2025-11-08 06:40:20 Age [y:d:h:m:s]: 00:056:07:45:21
Block: 1407471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40343 RingCT/type: yes/0
Extra: 01e029ed3c65f8ab89f934e0a0a5aa7669d17fec0afa68761687471cdfa9aeae9d02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 699eb0624f6cd81398a7a6e17104be60cbdaaa1d3e30ebec3dbc1f2f58471d46 0.600000000000 1895892 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": 1407481, "vin": [ { "gen": { "height": 1407471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "699eb0624f6cd81398a7a6e17104be60cbdaaa1d3e30ebec3dbc1f2f58471d46" } } ], "extra": [ 1, 224, 41, 237, 60, 101, 248, 171, 137, 249, 52, 224, 160, 165, 170, 118, 105, 209, 127, 236, 10, 250, 104, 118, 22, 135, 71, 28, 223, 169, 174, 174, 157, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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