Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d3c8d9528d41e5668839bfa0413b186fb93dcdf953ffc324dee76d06cb775dd

Tx prefix hash: adeb170a4ce7d6f55513a405b2b6fcd178507915635c2c998bd8a313284619b7
Tx public key: b80c2b2370697098d85c5963e6249edece04c36f932fcbf94a020ea2c96da6ae
Timestamp: 1735967400 Timestamp [UCT]: 2025-01-04 05:10:00 Age [y:d:h:m:s]: 00:109:23:52:17
Block: 1189809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78402 RingCT/type: yes/0
Extra: 01b80c2b2370697098d85c5963e6249edece04c36f932fcbf94a020ea2c96da6ae02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 562446611ad4172f9e6b0902267b73184d53ada4ad9c3df5916b9aa0c061b7ed 0.600000000000 1676320 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": 1189819, "vin": [ { "gen": { "height": 1189809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "562446611ad4172f9e6b0902267b73184d53ada4ad9c3df5916b9aa0c061b7ed" } } ], "extra": [ 1, 184, 12, 43, 35, 112, 105, 112, 152, 216, 92, 89, 99, 230, 36, 158, 222, 206, 4, 195, 111, 147, 47, 203, 249, 74, 2, 14, 162, 201, 109, 166, 174, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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