Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 928453e666ddd5d10d2dfc384e223472087e3b13ef764bcc4865e7e1a5b10952

Tx prefix hash: 74a5c30e5eb7f78cf7308963989ae1cd2bfb5be0cab1be0e6837ce59f16c53c7
Tx public key: 28e6040e9559708a18d6e9b3e9c710c8bf183fc905080a56e6915dee86432404
Timestamp: 1736726451 Timestamp [UCT]: 2025-01-13 00:00:51 Age [y:d:h:m:s]: 00:074:18:03:34
Block: 1196074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53208 RingCT/type: yes/0
Extra: 0128e6040e9559708a18d6e9b3e9c710c8bf183fc905080a56e6915dee864324040211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40bd812f113b16895e45a18192762c3c49a3a1a1456d564f8238898ee3d541f8 0.600000000000 1682671 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": 1196084, "vin": [ { "gen": { "height": 1196074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40bd812f113b16895e45a18192762c3c49a3a1a1456d564f8238898ee3d541f8" } } ], "extra": [ 1, 40, 230, 4, 14, 149, 89, 112, 138, 24, 214, 233, 179, 233, 199, 16, 200, 191, 24, 63, 201, 5, 8, 10, 86, 230, 145, 93, 238, 134, 67, 36, 4, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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