Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6f1cda5fdac3cfe75a942d21942caa80b0e4c7b59fed0877cb29e43bb8a43d9

Tx prefix hash: 4e1b1c41fb2d04270363b677cad3e2cb97cea54324798c258233513c9d20c828
Tx public key: f8131fa7e483e959f40d54a6a0bf565befb5a298652489c04a8b626c81326eb3
Timestamp: 1732803361 Timestamp [UCT]: 2024-11-28 14:16:01 Age [y:d:h:m:s]: 00:116:06:49:53
Block: 1163608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82901 RingCT/type: yes/0
Extra: 01f8131fa7e483e959f40d54a6a0bf565befb5a298652489c04a8b626c81326eb30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 926c913e7377e634744bb313afd33d63f9128088967e6894d9028d5c4256eac9 0.600000000000 1649275 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": 1163618, "vin": [ { "gen": { "height": 1163608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "926c913e7377e634744bb313afd33d63f9128088967e6894d9028d5c4256eac9" } } ], "extra": [ 1, 248, 19, 31, 167, 228, 131, 233, 89, 244, 13, 84, 166, 160, 191, 86, 91, 239, 181, 162, 152, 101, 36, 137, 192, 74, 139, 98, 108, 129, 50, 110, 179, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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