Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05c35fa6f3f988ce419936dbaa467f9a8b38f4ff98ddc682e13df3a770c4b5e9

Tx prefix hash: df46c48811a2857bdabe6296fae7e4cd3ff69e8a813be51fb498ba5a2fb05ab3
Tx public key: 55305d9fdf08f9f8ed84a34e4c17956b5c5afe6080fd56c56ceea0c813fd9f9d
Timestamp: 1714457502 Timestamp [UCT]: 2024-04-30 06:11:42 Age [y:d:h:m:s]: 01:191:15:50:25
Block: 1011602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395618 RingCT/type: yes/0
Extra: 0155305d9fdf08f9f8ed84a34e4c17956b5c5afe6080fd56c56ceea0c813fd9f9d0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf357fd6327e472fda80d9a7e91ecd335787e63d2381d16fff8931aba8d4b3a7 0.600000000000 1473874 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": 1011612, "vin": [ { "gen": { "height": 1011602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf357fd6327e472fda80d9a7e91ecd335787e63d2381d16fff8931aba8d4b3a7" } } ], "extra": [ 1, 85, 48, 93, 159, 223, 8, 249, 248, 237, 132, 163, 78, 76, 23, 149, 107, 92, 90, 254, 96, 128, 253, 86, 197, 108, 238, 160, 200, 19, 253, 159, 157, 2, 17, 0, 0, 0, 5, 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