Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5789524559375e79b2d404f44fea3038ac1aae4406cdb0495fa9dd834a61de6d

Tx prefix hash: dcb6bb23aaa5138742f004de4dbb7f563d6ad10bbd86a928444c873111c40e6d
Tx public key: ca0e3e3d832fba5cafcdd96de1f5d18345b4c8e86057fbfd43e84bc7ac8852e8
Timestamp: 1647023505 Timestamp [UCT]: 2022-03-11 18:31:45 Age [y:d:h:m:s]: 02:287:06:11:48
Block: 456286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724834 RingCT/type: yes/0
Extra: 01ca0e3e3d832fba5cafcdd96de1f5d18345b4c8e86057fbfd43e84bc7ac8852e802110000000cc9067537000000000000000000

1 output(s) for total of 18.885797914000 dcy

stealth address amount amount idx
00: c8d1702c8d7d0a4327edcb13cb0f3c6ab823e8b5b7f82aec78aa03a5be191eac 18.885797914000 872309 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": 456296, "vin": [ { "gen": { "height": 456286 } } ], "vout": [ { "amount": 18885797914, "target": { "key": "c8d1702c8d7d0a4327edcb13cb0f3c6ab823e8b5b7f82aec78aa03a5be191eac" } } ], "extra": [ 1, 202, 14, 62, 61, 131, 47, 186, 92, 175, 205, 217, 109, 225, 245, 209, 131, 69, 180, 200, 232, 96, 87, 251, 253, 67, 232, 75, 199, 172, 136, 82, 232, 2, 17, 0, 0, 0, 12, 201, 6, 117, 55, 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