Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 144b16bced89c8f70ab845f8a5c56f4f6d7b92500e84e7c398561624f55d6ffb

Tx prefix hash: 67a9dfbed9eab37935bb7ff4c248e20f687622cad4f7980fc8ebaba7265f1a99
Tx public key: 2acb2ed2d3fc156b74fd7557a28aa716148983dbfd33854b3aa5a53bc9d7cba2
Timestamp: 1711814064 Timestamp [UCT]: 2024-03-30 15:54:24 Age [y:d:h:m:s]: 01:024:04:53:16
Block: 989711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278248 RingCT/type: yes/0
Extra: 012acb2ed2d3fc156b74fd7557a28aa716148983dbfd33854b3aa5a53bc9d7cba20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 409a93a3394e057517ce6cfbc9608f70dca8d66e20aa4582f34d63e83d359ab4 0.600000000000 1450029 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": 989721, "vin": [ { "gen": { "height": 989711 } } ], "vout": [ { "amount": 600000000, "target": { "key": "409a93a3394e057517ce6cfbc9608f70dca8d66e20aa4582f34d63e83d359ab4" } } ], "extra": [ 1, 42, 203, 46, 210, 211, 252, 21, 107, 116, 253, 117, 87, 162, 138, 167, 22, 20, 137, 131, 219, 253, 51, 133, 75, 58, 165, 165, 59, 201, 215, 203, 162, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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