Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01c6b6471693f6f0d93999fd354bf85ffb6a2dc686b2a0396880a7b02b7dbc34

Tx prefix hash: 6f9ea0bfe88b768b38d75dcd35206f97e7680a24c0fe21fd8998d0017cc3ec03
Tx public key: ec1ec85b9745911174a806b32c9d164ce586aeebad90d5e450690fe0ceb7d185
Timestamp: 1694240117 Timestamp [UCT]: 2023-09-09 06:15:17 Age [y:d:h:m:s]: 02:060:22:59:48
Block: 844175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 563261 RingCT/type: yes/0
Extra: 01ec1ec85b9745911174a806b32c9d164ce586aeebad90d5e450690fe0ceb7d18502110000000775e3f0e9000000000000000000

1 output(s) for total of 0.979259642000 dcy

stealth address amount amount idx
00: c0348ee4fb70e851cdf6cd38f7f8bc107a040e9daec6b0991d70e29ca72d8fdc 0.979259642000 1297469 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": 844185, "vin": [ { "gen": { "height": 844175 } } ], "vout": [ { "amount": 979259642, "target": { "key": "c0348ee4fb70e851cdf6cd38f7f8bc107a040e9daec6b0991d70e29ca72d8fdc" } } ], "extra": [ 1, 236, 30, 200, 91, 151, 69, 145, 17, 116, 168, 6, 179, 44, 157, 22, 76, 229, 134, 174, 235, 173, 144, 213, 228, 80, 105, 15, 224, 206, 183, 209, 133, 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