Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81223224f00500230bc0afec4a65ffccd88043f0192a1486cb1af684c4ed4cee

Tx prefix hash: 5270c833771aeb740eb45e964a2e572b44bc04673f7e8e9fa70c1a5f0780353c
Tx public key: 3600c63defd421d3e5713eb955851f9f7ba9b1adc7516d595d638e5ef68754b6
Timestamp: 1726828437 Timestamp [UCT]: 2024-09-20 10:33:57 Age [y:d:h:m:s]: 00:244:14:09:03
Block: 1114166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174670 RingCT/type: yes/0
Extra: 013600c63defd421d3e5713eb955851f9f7ba9b1adc7516d595d638e5ef68754b602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b6f31cb2d783f5fb0692f2ea9d9a4096e01005118bd032de174d9812e65df3f 0.600000000000 1593965 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": 1114176, "vin": [ { "gen": { "height": 1114166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b6f31cb2d783f5fb0692f2ea9d9a4096e01005118bd032de174d9812e65df3f" } } ], "extra": [ 1, 54, 0, 198, 61, 239, 212, 33, 211, 229, 113, 62, 185, 85, 133, 31, 159, 123, 169, 177, 173, 199, 81, 109, 89, 93, 99, 142, 94, 246, 135, 84, 182, 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