Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 365fee0e0be1b7c73cd3d73262fda4e28b62d970d154fdd7ea2dfc31a8688a13

Tx prefix hash: fd337a8ff053d2676bd558509a434c1c8f1c0ab180e34dca1fa14670c68d02e4
Tx public key: 903fe13292fa91f2a1180f9dde4445a9f1fb7bcfdc0f4de44f7dc1d527a0af86
Timestamp: 1697465624 Timestamp [UCT]: 2023-10-16 14:13:44 Age [y:d:h:m:s]: 01:095:16:54:51
Block: 870939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329614 RingCT/type: yes/0
Extra: 01903fe13292fa91f2a1180f9dde4445a9f1fb7bcfdc0f4de44f7dc1d527a0af8602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.798394571000 dcy

stealth address amount amount idx
00: 0164c2783fca9ec21b76bc64383a2aef2a8d52b06b21c27dee7afdd69d3306c6 0.798394571000 1325900 of 0

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": 870949, "vin": [ { "gen": { "height": 870939 } } ], "vout": [ { "amount": 798394571, "target": { "key": "0164c2783fca9ec21b76bc64383a2aef2a8d52b06b21c27dee7afdd69d3306c6" } } ], "extra": [ 1, 144, 63, 225, 50, 146, 250, 145, 242, 161, 24, 15, 157, 222, 68, 69, 169, 241, 251, 123, 207, 220, 15, 77, 228, 79, 125, 193, 213, 39, 160, 175, 134, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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