Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 232ae325c00fddba5ac530c8cbcbd9bd2444f945c80e935004fb57b555f62160

Tx prefix hash: d9b8e795b99cdee4973c50bc0c94a08e49c689701faa70a79b2d6d034902c7f4
Tx public key: 8affe8e9beae27a71f23d4db665ffeb5d486ea00c4129adfe207b0231d29c87c
Timestamp: 1623023762 Timestamp [UCT]: 2021-06-06 23:56:02 Age [y:d:h:m:s]: 03:175:04:55:16
Block: 273534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 889788 RingCT/type: yes/0
Extra: 018affe8e9beae27a71f23d4db665ffeb5d486ea00c4129adfe207b0231d29c87c0211000000083634f08d000000000000000000

1 output(s) for total of 76.149812353000 dcy

stealth address amount amount idx
00: b5c3eafab49d1c78d16e3c08db8d72774a1e1e8d0c8d590aeadd218d5c4c2644 76.149812353000 573883 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": 273544, "vin": [ { "gen": { "height": 273534 } } ], "vout": [ { "amount": 76149812353, "target": { "key": "b5c3eafab49d1c78d16e3c08db8d72774a1e1e8d0c8d590aeadd218d5c4c2644" } } ], "extra": [ 1, 138, 255, 232, 233, 190, 174, 39, 167, 31, 35, 212, 219, 102, 95, 254, 181, 212, 134, 234, 0, 196, 18, 154, 223, 226, 7, 176, 35, 29, 41, 200, 124, 2, 17, 0, 0, 0, 8, 54, 52, 240, 141, 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