Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86e7f5158e1a22aca2512d7d68174fa2c7d1b9f3bed84cceeb01dc058869bb25

Tx prefix hash: d97c627be6f5b830fe6efb0aa3be4defdba109774ca62214da35687d3015a34f
Tx public key: 7bf175742f252d92733c63a53f22443ddae0d0abf134b39c6b63c4e1007ff162
Timestamp: 1713971320 Timestamp [UCT]: 2024-04-24 15:08:40 Age [y:d:h:m:s]: 00:306:08:21:54
Block: 1007573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218972 RingCT/type: yes/0
Extra: 017bf175742f252d92733c63a53f22443ddae0d0abf134b39c6b63c4e1007ff1620211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9102f39d65df6fd1125e7835d28ee822e86d4f806ab725117e7e7955eba6f3f5 0.600000000000 1468961 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": 1007583, "vin": [ { "gen": { "height": 1007573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9102f39d65df6fd1125e7835d28ee822e86d4f806ab725117e7e7955eba6f3f5" } } ], "extra": [ 1, 123, 241, 117, 116, 47, 37, 45, 146, 115, 60, 99, 165, 63, 34, 68, 61, 218, 224, 208, 171, 241, 52, 179, 156, 107, 99, 196, 225, 0, 127, 241, 98, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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