Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d1dc71fa7e705e47979df6455cd3767d17b94a560f903c80ee456365951d3c1

Tx prefix hash: c685bb03a1840306e028c1d9a4f73c3ff4a93cca090a194135980732362f0cb9
Tx public key: 5a8af7c287e1c1135ad446b03cf501707c347e20c9ce57e14e27aa9987787b1b
Timestamp: 1686065734 Timestamp [UCT]: 2023-06-06 15:35:34 Age [y:d:h:m:s]: 01:336:16:08:04
Block: 776476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501825 RingCT/type: yes/0
Extra: 015a8af7c287e1c1135ad446b03cf501707c347e20c9ce57e14e27aa9987787b1b02110000000775e3f0e9000000000000000000

1 output(s) for total of 1.641394016000 dcy

stealth address amount amount idx
00: 4c05096580edbf5fda53e454b95aea34de0d98057dc752f2733bf37b4b6858de 1.641394016000 1226031 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": 776486, "vin": [ { "gen": { "height": 776476 } } ], "vout": [ { "amount": 1641394016, "target": { "key": "4c05096580edbf5fda53e454b95aea34de0d98057dc752f2733bf37b4b6858de" } } ], "extra": [ 1, 90, 138, 247, 194, 135, 225, 193, 19, 90, 212, 70, 176, 60, 245, 1, 112, 124, 52, 126, 32, 201, 206, 87, 225, 78, 39, 170, 153, 135, 120, 123, 27, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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