Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a5eb28efd8297d8ec4c19bbe0721c5045aa86b4e22331f1b87df17f8b2c0ceb

Tx prefix hash: f0259728649d2e0db5d6e5859c2a6617948a75b9737d6c5a5796a8d2961452a3
Tx public key: c879f13574e0e04f484bc870217c424400408d8fc5338dab11bb42ce7c9642e9
Timestamp: 1711323802 Timestamp [UCT]: 2024-03-24 23:43:22 Age [y:d:h:m:s]: 00:234:10:24:34
Block: 985646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167812 RingCT/type: yes/0
Extra: 01c879f13574e0e04f484bc870217c424400408d8fc5338dab11bb42ce7c9642e90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b0949b35218d49a242cc876eacc46399a22f2c405e023c3e542a6581d1e67c1 0.600000000000 1445863 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": 985656, "vin": [ { "gen": { "height": 985646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b0949b35218d49a242cc876eacc46399a22f2c405e023c3e542a6581d1e67c1" } } ], "extra": [ 1, 200, 121, 241, 53, 116, 224, 224, 79, 72, 75, 200, 112, 33, 124, 66, 68, 0, 64, 141, 143, 197, 51, 141, 171, 17, 187, 66, 206, 124, 150, 66, 233, 2, 17, 0, 0, 0, 2, 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