Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f708b5da23ec5530a2e33128d28d6df67e0d0f1e2854027b8770bc6c0d5086c

Tx prefix hash: b698093d965e7f154716ca15234795b0a84ee0bddaab8fa793cc6256d56a2492
Tx public key: a0521d240d9bc3598235026fb1de57f279f97f24a082263f010dd101d3a07e62
Timestamp: 1694858511 Timestamp [UCT]: 2023-09-16 10:01:51 Age [y:d:h:m:s]: 01:129:10:56:02
Block: 849304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353795 RingCT/type: yes/0
Extra: 01a0521d240d9bc3598235026fb1de57f279f97f24a082263f010dd101d3a07e62021100000001faf35c9c000000000000000000

1 output(s) for total of 0.941679992000 dcy

stealth address amount amount idx
00: cb865aabd555cc93c40df75934e0ba30ccf5cb1e6efcbe4e1d8a14d00d2b9c67 0.941679992000 1302962 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": 849314, "vin": [ { "gen": { "height": 849304 } } ], "vout": [ { "amount": 941679992, "target": { "key": "cb865aabd555cc93c40df75934e0ba30ccf5cb1e6efcbe4e1d8a14d00d2b9c67" } } ], "extra": [ 1, 160, 82, 29, 36, 13, 155, 195, 89, 130, 53, 2, 111, 177, 222, 87, 242, 121, 249, 127, 36, 160, 130, 38, 63, 1, 13, 209, 1, 211, 160, 126, 98, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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