Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c206118eedb2cd4678b90b29a1edef3be599dbbe13985d29303118c27cd07fb7

Tx prefix hash: 73b0d03f78e2026f685fc1b874b39e01de3ea947af67b64ca05257c7c49b9c4f
Tx public key: 980424923bf57f972cdeaddc155bee8104f59503fe2026ce65a4e838ed3c7f98
Timestamp: 1592761171 Timestamp [UCT]: 2020-06-21 17:39:31 Age [y:d:h:m:s]: 04:148:18:49:55
Block: 110169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1044807 RingCT/type: yes/0
Extra: 01980424923bf57f972cdeaddc155bee8104f59503fe2026ce65a4e838ed3c7f9802110000002946a11e8a000000000000000000

1 output(s) for total of 264.828741961000 dcy

stealth address amount amount idx
00: 3fb7c80d75812a86e2813008184ad8d7b10583e9c72aa2c85d0d19196edbad4c 264.828741961000 190801 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": 110179, "vin": [ { "gen": { "height": 110169 } } ], "vout": [ { "amount": 264828741961, "target": { "key": "3fb7c80d75812a86e2813008184ad8d7b10583e9c72aa2c85d0d19196edbad4c" } } ], "extra": [ 1, 152, 4, 36, 146, 59, 245, 127, 151, 44, 222, 173, 220, 21, 91, 238, 129, 4, 245, 149, 3, 254, 32, 38, 206, 101, 164, 232, 56, 237, 60, 127, 152, 2, 17, 0, 0, 0, 41, 70, 161, 30, 138, 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