Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9302c129480a1c1468f24030bfb0cd93631a012d66267c05ac31c5b1fc54eef5

Tx prefix hash: 91c807882d463ebde7f5226a53aa807878723a2cf0ac454f03d123ab0aad0be8
Tx public key: cb5cde4b136a10cf2bbff5f1851c346e23c2dcfd3309b196f357f9cd58e1bae4
Timestamp: 1709256298 Timestamp [UCT]: 2024-03-01 01:24:58 Age [y:d:h:m:s]: 01:040:02:56:41
Block: 968496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289680 RingCT/type: yes/0
Extra: 01cb5cde4b136a10cf2bbff5f1851c346e23c2dcfd3309b196f357f9cd58e1bae40211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0af07f2aa210658e6652fa96752ed6e6ce55dd3a2e907a5aabaca484bdd93f4 0.600000000000 1428311 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": 968506, "vin": [ { "gen": { "height": 968496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0af07f2aa210658e6652fa96752ed6e6ce55dd3a2e907a5aabaca484bdd93f4" } } ], "extra": [ 1, 203, 92, 222, 75, 19, 106, 16, 207, 43, 191, 245, 241, 133, 28, 52, 110, 35, 194, 220, 253, 51, 9, 177, 150, 243, 87, 249, 205, 88, 225, 186, 228, 2, 17, 0, 0, 0, 7, 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