Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16e4a60502ec292249535381a75fad8e341a72777968b9eb7213481f33d5cc6d

Tx prefix hash: 1bad258bac191e690c16a4009c932c2fa1b2ca9f22b5132313600e8175bf613c
Tx public key: 921feb410b6c5970e51be0aad21c2266d932dc6f58950d2bea61d98a14d7fd5d
Timestamp: 1725088037 Timestamp [UCT]: 2024-08-31 07:07:17 Age [y:d:h:m:s]: 00:089:13:08:10
Block: 1099740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64040 RingCT/type: yes/0
Extra: 01921feb410b6c5970e51be0aad21c2266d932dc6f58950d2bea61d98a14d7fd5d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24e54de68b6c72f15e71b2706270965c5fe87ec059e59c181f849e75c205801a 0.600000000000 1575707 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": 1099750, "vin": [ { "gen": { "height": 1099740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24e54de68b6c72f15e71b2706270965c5fe87ec059e59c181f849e75c205801a" } } ], "extra": [ 1, 146, 31, 235, 65, 11, 108, 89, 112, 229, 27, 224, 170, 210, 28, 34, 102, 217, 50, 220, 111, 88, 149, 13, 43, 234, 97, 217, 138, 20, 215, 253, 93, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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