Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88a0722c1ce05be7c74f5e7edf0504dc38127db0f9c537f5f43078020dde49e3

Tx prefix hash: 65af4fc5c6cfe4ff976f6379fddeb2ba3093b53e7db8269d58a4271b87ca6517
Tx public key: 859d7e808c150bbe9f65865f1cea0d517ae032c2eb7471fc3ca3a5a3d6fa8086
Timestamp: 1718121659 Timestamp [UCT]: 2024-06-11 16:00:59 Age [y:d:h:m:s]: 00:173:22:34:52
Block: 1041992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124479 RingCT/type: yes/0
Extra: 01859d7e808c150bbe9f65865f1cea0d517ae032c2eb7471fc3ca3a5a3d6fa80860211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c66d620e8ee592f47b470c94265e3758e3dbc9dabd757627e31a84ae12119a6 0.600000000000 1510799 of 15

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": 1042002, "vin": [ { "gen": { "height": 1041992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c66d620e8ee592f47b470c94265e3758e3dbc9dabd757627e31a84ae12119a6" } } ], "extra": [ 1, 133, 157, 126, 128, 140, 21, 11, 190, 159, 101, 134, 95, 28, 234, 13, 81, 122, 224, 50, 194, 235, 116, 113, 252, 60, 163, 165, 163, 214, 250, 128, 134, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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