Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1853617b67b6e50ca305ecceb4d6e5dc9c20274b08ac59c39747b472c01b89e

Tx prefix hash: 7971f8e9faf09a42f0f331acf02351006c51aaed7be9389da214b1279c5cc4d6
Tx public key: 76a6ee9b48d6dda136b8fa03b14122fb040734a22b1dfef75682f8b8d1a43548
Timestamp: 1705032458 Timestamp [UCT]: 2024-01-12 04:07:38 Age [y:d:h:m:s]: 01:103:22:05:47
Block: 933446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335395 RingCT/type: yes/0
Extra: 0176a6ee9b48d6dda136b8fa03b14122fb040734a22b1dfef75682f8b8d1a4354802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acc76875eacadc1a2729e626eeb5142fcc48db3a87ce8085786a875c4ef30d31 0.600000000000 1391408 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": 933456, "vin": [ { "gen": { "height": 933446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acc76875eacadc1a2729e626eeb5142fcc48db3a87ce8085786a875c4ef30d31" } } ], "extra": [ 1, 118, 166, 238, 155, 72, 214, 221, 161, 54, 184, 250, 3, 177, 65, 34, 251, 4, 7, 52, 162, 43, 29, 254, 247, 86, 130, 248, 184, 209, 164, 53, 72, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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