Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4905d24211fe41bf5e485fd1c6d77d0fd24e2ddf3091843cc57288a54421090c

Tx prefix hash: 7dfe00c5e2ecd87c7fb73123528478fc23007efa2517de2c127caad59f9ab112
Tx public key: 3cc06b23c23386fb1d8f1fddc59662d64d627fec6896bea8fb5ecf97f8ddd7b4
Timestamp: 1723355969 Timestamp [UCT]: 2024-08-11 05:59:29 Age [y:d:h:m:s]: 00:241:21:38:21
Block: 1085373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172781 RingCT/type: yes/0
Extra: 013cc06b23c23386fb1d8f1fddc59662d64d627fec6896bea8fb5ecf97f8ddd7b4021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9ad2af48b98ea8e1492d5e59d044973f5f777bbcd689f2509908387e6f114e0 0.600000000000 1559946 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": 1085383, "vin": [ { "gen": { "height": 1085373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9ad2af48b98ea8e1492d5e59d044973f5f777bbcd689f2509908387e6f114e0" } } ], "extra": [ 1, 60, 192, 107, 35, 194, 51, 134, 251, 29, 143, 31, 221, 197, 150, 98, 214, 77, 98, 127, 236, 104, 150, 190, 168, 251, 94, 207, 151, 248, 221, 215, 180, 2, 17, 0, 0, 0, 6, 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