Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b563e89dd42d9960229759bb66e3d0097af368780e0c3026f9907336b33d13a3

Tx prefix hash: 5509697cb42aaa45818f1b056d534c416317984f61880c2e436f34a028b9fb76
Tx public key: 58bcc7ecf773c027d42d0b1eece35cf40221308e51c361bf38b499f5095a4e9e
Timestamp: 1712485785 Timestamp [UCT]: 2024-04-07 10:29:45 Age [y:d:h:m:s]: 01:213:06:43:37
Block: 995228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411112 RingCT/type: yes/0
Extra: 0158bcc7ecf773c027d42d0b1eece35cf40221308e51c361bf38b499f5095a4e9e02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1fb51b9aefc9dc0413fbb5c6d233ee18edb55811f4e7ba861451cda581c10b7 0.600000000000 1455634 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": 995238, "vin": [ { "gen": { "height": 995228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1fb51b9aefc9dc0413fbb5c6d233ee18edb55811f4e7ba861451cda581c10b7" } } ], "extra": [ 1, 88, 188, 199, 236, 247, 115, 192, 39, 212, 45, 11, 30, 236, 227, 92, 244, 2, 33, 48, 142, 81, 195, 97, 191, 56, 180, 153, 245, 9, 90, 78, 158, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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