Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6334712936283c4f0b7669545704bab8213b38a9ef69ea235e878b4d95b06b91

Tx prefix hash: 74eea9aa923edc4d5cda2cbdf77d6d41ad69ecc95402cd6c2e9b5493c83f6a38
Tx public key: c366873f7e9f56884b01b243ce459a9888a33775877aa4f05b70a27cffde5de1
Timestamp: 1710360480 Timestamp [UCT]: 2024-03-13 20:08:00 Age [y:d:h:m:s]: 01:012:11:50:54
Block: 977659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269874 RingCT/type: yes/0
Extra: 01c366873f7e9f56884b01b243ce459a9888a33775877aa4f05b70a27cffde5de10211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 814f4c2e37c0b6609a799a2e1480d7293e7cada7ac0decffb42118d70fb222d4 0.600000000000 1437662 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": 977669, "vin": [ { "gen": { "height": 977659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "814f4c2e37c0b6609a799a2e1480d7293e7cada7ac0decffb42118d70fb222d4" } } ], "extra": [ 1, 195, 102, 135, 63, 126, 159, 86, 136, 75, 1, 178, 67, 206, 69, 154, 152, 136, 163, 55, 117, 135, 122, 164, 240, 91, 112, 162, 124, 255, 222, 93, 225, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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