Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f8ea88b2f686911a6fdcdf557a866a9c392d2a927611bd3410239cfeb94f938

Tx prefix hash: 6aec0f1d64ed9276c8d192a94d00a4e8490b16157408512f565cdf7704ea47aa
Tx public key: 1fc23b27237e1e74574d770e8f85f405189f91e4c19119dba49e89e63746ed71
Timestamp: 1715510661 Timestamp [UCT]: 2024-05-12 10:44:21 Age [y:d:h:m:s]: 00:289:09:40:42
Block: 1020370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206805 RingCT/type: yes/0
Extra: 011fc23b27237e1e74574d770e8f85f405189f91e4c19119dba49e89e63746ed7102110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e4be34d6f6b5b774b430b233ff1ea1db8de3da5523c458ecd8041a16ae6ce89 0.600000000000 1484435 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": 1020380, "vin": [ { "gen": { "height": 1020370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e4be34d6f6b5b774b430b233ff1ea1db8de3da5523c458ecd8041a16ae6ce89" } } ], "extra": [ 1, 31, 194, 59, 39, 35, 126, 30, 116, 87, 77, 119, 14, 143, 133, 244, 5, 24, 159, 145, 228, 193, 145, 25, 219, 164, 158, 137, 230, 55, 70, 237, 113, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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