Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32cf722d49c87c3c0f0332877d2ea357967dd1b8c5fc9a4e3e40f20ed168343a

Tx prefix hash: d4ffe90655cdb40dcf9765636db9049ce72611e49be4d54d2409be517022f519
Tx public key: aa11959ccce2a844e8b85f74361bfdf7ab23b7b1c109dc6f22501d0a524b1b65
Timestamp: 1588730710 Timestamp [UCT]: 2020-05-06 02:05:10 Age [y:d:h:m:s]: 04:184:05:59:42
Block: 98495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1048467 RingCT/type: yes/0
Extra: 01aa11959ccce2a844e8b85f74361bfdf7ab23b7b1c109dc6f22501d0a524b1b6502110000000186362411000000000000000000

1 output(s) for total of 289.503249404000 dcy

stealth address amount amount idx
00: 43e569980643cffc9311943e97087b4fdf44148aa9f36c9764bf53209bbe2148 289.503249404000 174119 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": 98505, "vin": [ { "gen": { "height": 98495 } } ], "vout": [ { "amount": 289503249404, "target": { "key": "43e569980643cffc9311943e97087b4fdf44148aa9f36c9764bf53209bbe2148" } } ], "extra": [ 1, 170, 17, 149, 156, 204, 226, 168, 68, 232, 184, 95, 116, 54, 27, 253, 247, 171, 35, 183, 177, 193, 9, 220, 111, 34, 80, 29, 10, 82, 75, 27, 101, 2, 17, 0, 0, 0, 1, 134, 54, 36, 17, 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