Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344aeab36097a5e3cca35ae7f7b83d15dd17614fd4ae0c4994e0da612c115372

Tx prefix hash: ffddc1d93b6fadcc954592fc4a02b7d1c2ffcc06381c7036250830f303af6e95
Tx public key: 668da2fd88f1122dbaf1b2285d64a184a31335ddf9fb6e0f0cdb126d79ab2ceb
Timestamp: 1731169878 Timestamp [UCT]: 2024-11-09 16:31:18 Age [y:d:h:m:s]: 00:014:21:21:10
Block: 1150077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10653 RingCT/type: yes/0
Extra: 01668da2fd88f1122dbaf1b2285d64a184a31335ddf9fb6e0f0cdb126d79ab2ceb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 934c61b1b6276849679f80bbcfd8d809e31eaf0a1bfa29574fa7c94d8e966230 0.600000000000 1635278 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": 1150087, "vin": [ { "gen": { "height": 1150077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "934c61b1b6276849679f80bbcfd8d809e31eaf0a1bfa29574fa7c94d8e966230" } } ], "extra": [ 1, 102, 141, 162, 253, 136, 241, 18, 45, 186, 241, 178, 40, 93, 100, 161, 132, 163, 19, 53, 221, 249, 251, 110, 15, 12, 219, 18, 109, 121, 171, 44, 235, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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