Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28622ceefa0981986f2ab5cb26a10ee19bcca35f4c5c02611b1290891c8061d3

Tx prefix hash: 0538b32805988bf23b88354120ffa3e331d82015c8d1f9b3ba76cb6826b3c739
Tx public key: 6365a577c7dc828aa7ff02b8e11b568631c07cccea672648c33e1f1a7c1348a8
Timestamp: 1713434568 Timestamp [UCT]: 2024-04-18 10:02:48 Age [y:d:h:m:s]: 00:317:03:26:15
Block: 1003114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226712 RingCT/type: yes/0
Extra: 016365a577c7dc828aa7ff02b8e11b568631c07cccea672648c33e1f1a7c1348a80211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff5c0d9b9145e898f011a77724056079aae9997a12f8ff9dac2a6c5a3a645d27 0.600000000000 1463644 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": 1003124, "vin": [ { "gen": { "height": 1003114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff5c0d9b9145e898f011a77724056079aae9997a12f8ff9dac2a6c5a3a645d27" } } ], "extra": [ 1, 99, 101, 165, 119, 199, 220, 130, 138, 167, 255, 2, 184, 225, 27, 86, 134, 49, 192, 124, 204, 234, 103, 38, 72, 195, 62, 31, 26, 124, 19, 72, 168, 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