Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f88c49c213f89969247d9f4b9007033f50480c3ed9f8db3564da8dbed64fc81a

Tx prefix hash: 2827d63c29dd18c2b1ea6d0a22be9e8412a8f0e92df1ff6f3ee029d7050ae348
Tx public key: e2c7cf6f2900ce69500ce87da5b4091d16dc347e9966b8a8f9e606d3368b0f30
Timestamp: 1697524853 Timestamp [UCT]: 2023-10-17 06:40:53 Age [y:d:h:m:s]: 01:168:08:47:51
Block: 871425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381359 RingCT/type: yes/0
Extra: 01e2c7cf6f2900ce69500ce87da5b4091d16dc347e9966b8a8f9e606d3368b0f30021100000002faf35c9c000000000000000000

1 output(s) for total of 0.795439685000 dcy

stealth address amount amount idx
00: 197fc5fb8f3a27e593d40a4df9b37b489234e2ea29e65abf645c035341c53ab5 0.795439685000 1326406 of 0

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": 871435, "vin": [ { "gen": { "height": 871425 } } ], "vout": [ { "amount": 795439685, "target": { "key": "197fc5fb8f3a27e593d40a4df9b37b489234e2ea29e65abf645c035341c53ab5" } } ], "extra": [ 1, 226, 199, 207, 111, 41, 0, 206, 105, 80, 12, 232, 125, 165, 180, 9, 29, 22, 220, 52, 126, 153, 102, 184, 168, 249, 230, 6, 211, 54, 139, 15, 48, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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