Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2adb219b5a70009d79f1b84aa4b5d8a40777566c7780f4c685ca008a5bcaf8b5

Tx prefix hash: 2fff7f5b99d49622eff468619a21a16bd5e23866a660ce85494653d103dfce72
Tx public key: 7c0a2dbff0a513da4b902f9bd0c78cae4f2fd9ade83f858c6c29e159cc21c632
Timestamp: 1727073502 Timestamp [UCT]: 2024-09-23 06:38:22 Age [y:d:h:m:s]: 00:191:19:39:44
Block: 1116208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136884 RingCT/type: yes/0
Extra: 017c0a2dbff0a513da4b902f9bd0c78cae4f2fd9ade83f858c6c29e159cc21c632021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8a033bc589e194b065684ddab505383423618efd73778d7240c3a44882907e2 0.600000000000 1596607 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": 1116218, "vin": [ { "gen": { "height": 1116208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8a033bc589e194b065684ddab505383423618efd73778d7240c3a44882907e2" } } ], "extra": [ 1, 124, 10, 45, 191, 240, 165, 19, 218, 75, 144, 47, 155, 208, 199, 140, 174, 79, 47, 217, 173, 232, 63, 133, 140, 108, 41, 225, 89, 204, 33, 198, 50, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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