Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1745d20261c5a10d11f35648327d4f6ccade5bd6719a92a53e536f7bf629bdd

Tx prefix hash: a5e5d3033b64a9b98107ac9102971774910336f0bac7fdd1ecec30a8b88f98e7
Tx public key: 09aae2ed43373aaa1fc92e93562fa06c2b6d06eccb6a180249b04aae9e95d67b
Timestamp: 1699785933 Timestamp [UCT]: 2023-11-12 10:45:33 Age [y:d:h:m:s]: 01:104:03:00:15
Block: 889969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335565 RingCT/type: yes/0
Extra: 0109aae2ed43373aaa1fc92e93562fa06c2b6d06eccb6a180249b04aae9e95d67b0211000000014b8f5122000000000000000000

1 output(s) for total of 0.690499323000 dcy

stealth address amount amount idx
00: e560959c3e7d94ca72ad69478a04d1aeee3d9a976d8c3199fce63c9e226fa87a 0.690499323000 1345988 of 0

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": 889979, "vin": [ { "gen": { "height": 889969 } } ], "vout": [ { "amount": 690499323, "target": { "key": "e560959c3e7d94ca72ad69478a04d1aeee3d9a976d8c3199fce63c9e226fa87a" } } ], "extra": [ 1, 9, 170, 226, 237, 67, 55, 58, 170, 31, 201, 46, 147, 86, 47, 160, 108, 43, 109, 6, 236, 203, 106, 24, 2, 73, 176, 74, 174, 158, 149, 214, 123, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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