Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bedf42de71f6d1be2b9024d9fbab9a43d5ef9ee2e5defe0340d2f7af65d141af

Tx prefix hash: 9ba23124b7c3f8a2a47da990153c66ed83e27cb69cb91cbd57077647e8bd6333
Tx public key: c7df44c00760683147f27605b0dae262fbafc2b4317c6d1e22899ced5a1911a3
Timestamp: 1720771599 Timestamp [UCT]: 2024-07-12 08:06:39 Age [y:d:h:m:s]: 01:121:05:57:51
Block: 1063960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345166 RingCT/type: yes/0
Extra: 01c7df44c00760683147f27605b0dae262fbafc2b4317c6d1e22899ced5a1911a302110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 560cd13f4bda40b1f164ac21d1920fef6efe79f4495a643b80dc4beb67f6231d 0.600000000000 1534481 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": 1063970, "vin": [ { "gen": { "height": 1063960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "560cd13f4bda40b1f164ac21d1920fef6efe79f4495a643b80dc4beb67f6231d" } } ], "extra": [ 1, 199, 223, 68, 192, 7, 96, 104, 49, 71, 242, 118, 5, 176, 218, 226, 98, 251, 175, 194, 180, 49, 124, 109, 30, 34, 137, 156, 237, 90, 25, 17, 163, 2, 17, 0, 0, 0, 17, 145, 225, 60, 4, 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