Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a80437d34085d46980e5d1355973ca6c62c711f82dfe3cc3954cc5653e6d87e

Tx prefix hash: 76d25f456d7a6c027d53797a08702b0ccea13cb4d21e13a14eadd1eab975bd73
Tx public key: bc6f19410f8161a809076dcbdde79e3a53009a35c790c3624f3c600c6a3b9454
Timestamp: 1694535784 Timestamp [UCT]: 2023-09-12 16:23:04 Age [y:d:h:m:s]: 01:121:02:02:26
Block: 846624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347862 RingCT/type: yes/0
Extra: 01bc6f19410f8161a809076dcbdde79e3a53009a35c790c3624f3c600c6a3b945402110000000675e3f0e9000000000000000000

1 output(s) for total of 0.961132581000 dcy

stealth address amount amount idx
00: e397c126dacf7747bcc338997c0e3dde97f429dddd35053a251a3ca953e77c84 0.961132581000 1300096 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": 846634, "vin": [ { "gen": { "height": 846624 } } ], "vout": [ { "amount": 961132581, "target": { "key": "e397c126dacf7747bcc338997c0e3dde97f429dddd35053a251a3ca953e77c84" } } ], "extra": [ 1, 188, 111, 25, 65, 15, 129, 97, 168, 9, 7, 109, 203, 221, 231, 158, 58, 83, 0, 154, 53, 199, 144, 195, 98, 79, 60, 96, 12, 106, 59, 148, 84, 2, 17, 0, 0, 0, 6, 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