Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16325673cd3955e1f1e4dae6f5101f9d8bbffe069a4abac4b809ac85d0e8ac9c

Tx prefix hash: d913d0881c3745e2f389c7e613a0e08e210e0c73b19972d4ce991c54ea1d4283
Tx public key: ada10f0d0a7a97e3115087936b00e71ce136c99e4a2d3e1d83bb51a60266e4c9
Timestamp: 1719124151 Timestamp [UCT]: 2024-06-23 06:29:11 Age [y:d:h:m:s]: 01:151:02:16:34
Block: 1050278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366549 RingCT/type: yes/0
Extra: 01ada10f0d0a7a97e3115087936b00e71ce136c99e4a2d3e1d83bb51a60266e4c90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 021bc448b2a5e2dff0576243a5c760fa45ef8d9126f4b5e8ad2f4c8575173ecf 0.600000000000 1520439 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": 1050288, "vin": [ { "gen": { "height": 1050278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "021bc448b2a5e2dff0576243a5c760fa45ef8d9126f4b5e8ad2f4c8575173ecf" } } ], "extra": [ 1, 173, 161, 15, 13, 10, 122, 151, 227, 17, 80, 135, 147, 107, 0, 231, 28, 225, 54, 201, 158, 74, 45, 62, 29, 131, 187, 81, 166, 2, 102, 228, 201, 2, 17, 0, 0, 0, 1, 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