Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2f8407518304d83cd9ba65a91ae96898916a4561d283377f20d1cc71b9a4cb8

Tx prefix hash: a159127167d1614f0ad354da5e396a7e18eff5ae738bd0b3e0d1f77bb98dca99
Tx public key: c3faed77c8f9dca204829d9ee7684d94c06721833af76eee0b580c96f40c0ec0
Timestamp: 1694876710 Timestamp [UCT]: 2023-09-16 15:05:10 Age [y:d:h:m:s]: 01:166:04:53:19
Block: 849459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379849 RingCT/type: yes/0
Extra: 01c3faed77c8f9dca204829d9ee7684d94c06721833af76eee0b580c96f40c0ec0021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.940567056000 dcy

stealth address amount amount idx
00: f2f0cfd4f78f415e743824fff41ef1e809a9281bccfa47c1d0daf4bae94082d5 0.940567056000 1303125 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": 849469, "vin": [ { "gen": { "height": 849459 } } ], "vout": [ { "amount": 940567056, "target": { "key": "f2f0cfd4f78f415e743824fff41ef1e809a9281bccfa47c1d0daf4bae94082d5" } } ], "extra": [ 1, 195, 250, 237, 119, 200, 249, 220, 162, 4, 130, 157, 158, 231, 104, 77, 148, 192, 103, 33, 131, 58, 247, 110, 238, 11, 88, 12, 150, 244, 12, 14, 192, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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