Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32c7040b15e5cb971b488a364e4f251498797b575153fd7a87879994da89a4d0

Tx prefix hash: 6cb7c69e38c6fe237cd53aa99ce949147df8969e6d850940a8d33e7455809128
Tx public key: f3271f47521be0a0b380c9dea5a41d9a3b3feafb19db8266a3b02b0132958948
Timestamp: 1703448640 Timestamp [UCT]: 2023-12-24 20:10:40 Age [y:d:h:m:s]: 01:174:06:39:46
Block: 920340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385626 RingCT/type: yes/0
Extra: 01f3271f47521be0a0b380c9dea5a41d9a3b3feafb19db8266a3b02b013295894802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d0cfd8e15b6353b218bba38e8089bf02d372559016de6353075baf6c6c40838 0.600000000000 1378018 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": 920350, "vin": [ { "gen": { "height": 920340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d0cfd8e15b6353b218bba38e8089bf02d372559016de6353075baf6c6c40838" } } ], "extra": [ 1, 243, 39, 31, 71, 82, 27, 224, 160, 179, 128, 201, 222, 165, 164, 29, 154, 59, 63, 234, 251, 25, 219, 130, 102, 163, 176, 43, 1, 50, 149, 137, 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