Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec7ec8c02e470f65637e0313cbdf942a21eaabc46de60f373c85bd6d98612511

Tx prefix hash: c61e2a832f476759ba714215fe17d4391d0612d9625f470a9edad8cfcec731b7
Tx public key: f59ce3f5d6142f77d8be09403ebab69c6ecc76f5270c78dd707e13f1a5d453b0
Timestamp: 1711622975 Timestamp [UCT]: 2024-03-28 10:49:35 Age [y:d:h:m:s]: 01:049:12:37:51
Block: 988121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296369 RingCT/type: yes/0
Extra: 01f59ce3f5d6142f77d8be09403ebab69c6ecc76f5270c78dd707e13f1a5d453b002110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2d7a2050b070567eacd3f0de66831d1049c9c15eb3b4c5fa391782d0f02e641 0.600000000000 1448388 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": 988131, "vin": [ { "gen": { "height": 988121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2d7a2050b070567eacd3f0de66831d1049c9c15eb3b4c5fa391782d0f02e641" } } ], "extra": [ 1, 245, 156, 227, 245, 214, 20, 47, 119, 216, 190, 9, 64, 62, 186, 182, 156, 110, 204, 118, 245, 39, 12, 120, 221, 112, 126, 19, 241, 165, 212, 83, 176, 2, 17, 0, 0, 0, 16, 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