Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e5e411ab4dc4d9a15e0ec1976870d511b1496bcdc9553f8a81fcfa2f73fba59

Tx prefix hash: 2c8a5ebfc918b7189d2894e03cfcb5be485ff39a99e27016e63a7fe7530108b9
Tx public key: bec1acd126fb4a70423fcce2631041612a6bf80a597c71d36a066f2f4393b2b7
Timestamp: 1706709973 Timestamp [UCT]: 2024-01-31 14:06:13 Age [y:d:h:m:s]: 01:294:16:51:30
Block: 947354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469421 RingCT/type: yes/0
Extra: 01bec1acd126fb4a70423fcce2631041612a6bf80a597c71d36a066f2f4393b2b702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8ea03c3fe968f3115a3bb6559ecebbdcc88086f72123350b2d9594d35ee499f 0.600000000000 1405702 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": 947364, "vin": [ { "gen": { "height": 947354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8ea03c3fe968f3115a3bb6559ecebbdcc88086f72123350b2d9594d35ee499f" } } ], "extra": [ 1, 190, 193, 172, 209, 38, 251, 74, 112, 66, 63, 204, 226, 99, 16, 65, 97, 42, 107, 248, 10, 89, 124, 113, 211, 106, 6, 111, 47, 67, 147, 178, 183, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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