Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c8db6065b7eea1db06edce0066a83e257f059b7a021428108bf64ffe413cd6e

Tx prefix hash: f6b3b466e4922deac4ea981ad46f8732f3eac484d23785b63cc3e0b2a3330af2
Tx public key: a470ee3c99a16c82ecb7815c1d897e22ca00fd9f62f80b5bee1d60d84866ba91
Timestamp: 1694265013 Timestamp [UCT]: 2023-09-09 13:10:13 Age [y:d:h:m:s]: 01:270:15:08:55
Block: 844382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454566 RingCT/type: yes/0
Extra: 01a470ee3c99a16c82ecb7815c1d897e22ca00fd9f62f80b5bee1d60d84866ba91021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.977714327000 dcy

stealth address amount amount idx
00: 1a8b0c32f006bd0fd8f284eb8691634ed9a9c66803c6d14f6c994777e9c89051 0.977714327000 1297686 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": 844392, "vin": [ { "gen": { "height": 844382 } } ], "vout": [ { "amount": 977714327, "target": { "key": "1a8b0c32f006bd0fd8f284eb8691634ed9a9c66803c6d14f6c994777e9c89051" } } ], "extra": [ 1, 164, 112, 238, 60, 153, 161, 108, 130, 236, 183, 129, 92, 29, 137, 126, 34, 202, 0, 253, 159, 98, 248, 11, 91, 238, 29, 96, 216, 72, 102, 186, 145, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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