Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cbb986601173ce6f9c2c87eebfe7a4d0ade78210a3e45d9cb0b924620a32335

Tx prefix hash: a5fd3996db6496a233a57eaebad1f03b07d479d66dae02e77f768ed1b6ff8ec3
Tx public key: 52c1893aa66b29da52a656607bd665f88fa60c4a32f8bef7914e511af61bd8eb
Timestamp: 1696023822 Timestamp [UCT]: 2023-09-29 21:43:42 Age [y:d:h:m:s]: 01:047:22:44:14
Block: 858983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295494 RingCT/type: yes/0
Extra: 0152c1893aa66b29da52a656607bd665f88fa60c4a32f8bef7914e511af61bd8eb0211000000024b8f5122000000000000000000

1 output(s) for total of 0.874646945000 dcy

stealth address amount amount idx
00: bdd07d1107cac6c215f364a85100a4d95dc8b11319c92522527f91d9933133f3 0.874646945000 1313187 of 0

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": 858993, "vin": [ { "gen": { "height": 858983 } } ], "vout": [ { "amount": 874646945, "target": { "key": "bdd07d1107cac6c215f364a85100a4d95dc8b11319c92522527f91d9933133f3" } } ], "extra": [ 1, 82, 193, 137, 58, 166, 107, 41, 218, 82, 166, 86, 96, 123, 214, 101, 248, 143, 166, 12, 74, 50, 248, 190, 247, 145, 78, 81, 26, 246, 27, 216, 235, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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