Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efbcdedd3f18d9e30a3cca6f8a16c4f6bb12f4deb1395347f040643452628983

Tx prefix hash: 3be66d50770b575a5e3920c0d76fda470219f8bb794341d75fba9c9e258fe0de
Tx public key: 960f16558b7a95bb967a6f67ea594acd82c851d17036aacc68c0660d9835d21e
Timestamp: 1727143973 Timestamp [UCT]: 2024-09-24 02:12:53 Age [y:d:h:m:s]: 00:193:19:12:27
Block: 1116783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138319 RingCT/type: yes/0
Extra: 01960f16558b7a95bb967a6f67ea594acd82c851d17036aacc68c0660d9835d21e021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8a61a02adb7d1f5cc3232356d660783950b4af17485c1eb6a00d3c4b0f215d5 0.600000000000 1597390 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": 1116793, "vin": [ { "gen": { "height": 1116783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8a61a02adb7d1f5cc3232356d660783950b4af17485c1eb6a00d3c4b0f215d5" } } ], "extra": [ 1, 150, 15, 22, 85, 139, 122, 149, 187, 150, 122, 111, 103, 234, 89, 74, 205, 130, 200, 81, 209, 112, 54, 170, 204, 104, 192, 102, 13, 152, 53, 210, 30, 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