Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeedc90410f097855ae7416ed8103832f0447f3d0eaccb55b5db3f553fad415a

Tx prefix hash: 93cb94a60001a6568684e9fa1ece1e7e8c1c0646e1f98ae3ddd559e4d6c18c6c
Tx public key: 3da1dc42a2d10eccbe558615fa8dd2343a014f386e46ba324641c60c30df02eb
Timestamp: 1728538390 Timestamp [UCT]: 2024-10-10 05:33:10 Age [y:d:h:m:s]: 01:029:22:44:04
Block: 1128343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279770 RingCT/type: yes/0
Extra: 013da1dc42a2d10eccbe558615fa8dd2343a014f386e46ba324641c60c30df02eb021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d1716f4ba083259d484180d4f5dc7723095456d6391cb6479b5820e65249186 0.600000000000 1611160 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": 1128353, "vin": [ { "gen": { "height": 1128343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d1716f4ba083259d484180d4f5dc7723095456d6391cb6479b5820e65249186" } } ], "extra": [ 1, 61, 161, 220, 66, 162, 209, 14, 204, 190, 85, 134, 21, 250, 141, 210, 52, 58, 1, 79, 56, 110, 70, 186, 50, 70, 65, 198, 12, 48, 223, 2, 235, 2, 17, 0, 0, 0, 2, 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