Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b25eab484a33df2b7fd6337643180cc06ae22c93d5a6775e10c714ba1d0211a4

Tx prefix hash: 0be783d9c670731093cf2e0eab998cfd3a3acbfcc7d5de1238de23265c072cab
Tx public key: 8f80e537d6aebb76b6568c3b881c964b4c1783548de33348c58e8ef2bf8f01ef
Timestamp: 1705650024 Timestamp [UCT]: 2024-01-19 07:40:24 Age [y:d:h:m:s]: 01:143:15:14:42
Block: 938564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363796 RingCT/type: yes/0
Extra: 018f80e537d6aebb76b6568c3b881c964b4c1783548de33348c58e8ef2bf8f01ef0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1a2c8d718c67561014df63901b84ddbfd17c9a0368c945464b6c23ce7a56ab9 0.600000000000 1396634 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": 938574, "vin": [ { "gen": { "height": 938564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1a2c8d718c67561014df63901b84ddbfd17c9a0368c945464b6c23ce7a56ab9" } } ], "extra": [ 1, 143, 128, 229, 55, 214, 174, 187, 118, 182, 86, 140, 59, 136, 28, 150, 75, 76, 23, 131, 84, 141, 227, 51, 72, 197, 142, 142, 242, 191, 143, 1, 239, 2, 17, 0, 0, 0, 4, 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