Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62def709324d5976ad25ac65823cbd40f7308d86eede2d1ac6f9fb3657b459ad

Tx prefix hash: f52cae3cf58e1738a176e71a832f11a65d6d48d9e281a80d3c696fd3b482218d
Tx public key: bee4641e83e6a301e1040a1796805f23ab445452fd5018e3ae3e7addd8888ba1
Timestamp: 1703478688 Timestamp [UCT]: 2023-12-25 04:31:28 Age [y:d:h:m:s]: 01:321:20:12:22
Block: 920593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488853 RingCT/type: yes/0
Extra: 01bee4641e83e6a301e1040a1796805f23ab445452fd5018e3ae3e7addd8888ba10211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 344aff5043c317816a92cc1dd1dc3bdbfec1ab68b63e8d3da2b2e51190d827ce 0.600000000000 1378273 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": 920603, "vin": [ { "gen": { "height": 920593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "344aff5043c317816a92cc1dd1dc3bdbfec1ab68b63e8d3da2b2e51190d827ce" } } ], "extra": [ 1, 190, 228, 100, 30, 131, 230, 163, 1, 225, 4, 10, 23, 150, 128, 95, 35, 171, 68, 84, 82, 253, 80, 24, 227, 174, 62, 122, 221, 216, 136, 139, 161, 2, 17, 0, 0, 0, 5, 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