Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e50bef22024bb96beb7f8e3be3ed5c6da0e3b6ebf75638f6078d57fec612756

Tx prefix hash: a799f06533c0bd5ee9ef5c2e3d9a9e5ca530406cd328444275a37b545ae09802
Tx public key: 812e0a9102e800ecdef185e3dc8797f954100c96be7aaeae3b56ec89479fe296
Timestamp: 1647623954 Timestamp [UCT]: 2022-03-18 17:19:14 Age [y:d:h:m:s]: 03:045:01:24:54
Block: 461237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 812378 RingCT/type: yes/0
Extra: 01812e0a9102e800ecdef185e3dc8797f954100c96be7aaeae3b56ec89479fe296021100000004cb8520c2000000000000000000

1 output(s) for total of 18.185724716000 dcy

stealth address amount amount idx
00: 2b1205c1186fad62598754cf2ff61e5c921563d44e6599765c8dc3bb6152010c 18.185724716000 878426 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": 461247, "vin": [ { "gen": { "height": 461237 } } ], "vout": [ { "amount": 18185724716, "target": { "key": "2b1205c1186fad62598754cf2ff61e5c921563d44e6599765c8dc3bb6152010c" } } ], "extra": [ 1, 129, 46, 10, 145, 2, 232, 0, 236, 222, 241, 133, 227, 220, 135, 151, 249, 84, 16, 12, 150, 190, 122, 174, 174, 59, 86, 236, 137, 71, 159, 226, 150, 2, 17, 0, 0, 0, 4, 203, 133, 32, 194, 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