Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83dd1257d96fba4f4ef70538a06938033ac91a61c32f19b374009fcd82001d5e

Tx prefix hash: b673399dbff2571419329cca9b8f04c0189c0a689bf9af51786a24850cc9cb4b
Tx public key: 1f1ea32ff516dccd51e2a9b428ce3f564b23bd72b92cbe2a81a6d5bd9e93051c
Timestamp: 1718697810 Timestamp [UCT]: 2024-06-18 08:03:30 Age [y:d:h:m:s]: 00:251:01:12:07
Block: 1046763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179357 RingCT/type: yes/0
Extra: 011f1ea32ff516dccd51e2a9b428ce3f564b23bd72b92cbe2a81a6d5bd9e93051c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97f63db3ab40c7d925ad1727dcb5825d893a308e237e60eda57988db5a461abe 0.600000000000 1516582 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": 1046773, "vin": [ { "gen": { "height": 1046763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97f63db3ab40c7d925ad1727dcb5825d893a308e237e60eda57988db5a461abe" } } ], "extra": [ 1, 31, 30, 163, 47, 245, 22, 220, 205, 81, 226, 169, 180, 40, 206, 63, 86, 75, 35, 189, 114, 185, 44, 190, 42, 129, 166, 213, 189, 158, 147, 5, 28, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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