Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43a147cb0a7029affbbd996b8eed479c4ae4629ee8d2b48060571a32fef024f2

Tx prefix hash: fc9614f794b7cebd5cae49c5ab8b69a098d3cd66e7dd336ed0c52e90ab1bda2e
Tx public key: 491ac4b684d558d74c43b665a44774184c5ffd2dd5b3d3018e4ec4a540ad7907
Timestamp: 1719569358 Timestamp [UCT]: 2024-06-28 10:09:18 Age [y:d:h:m:s]: 01:183:10:37:43
Block: 1053983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389714 RingCT/type: yes/0
Extra: 01491ac4b684d558d74c43b665a44774184c5ffd2dd5b3d3018e4ec4a540ad790702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e938415f01d6bc5a3b2f262d2b165245b8e05f7df166df79488438712b1f7ee6 0.600000000000 1524342 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": 1053993, "vin": [ { "gen": { "height": 1053983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e938415f01d6bc5a3b2f262d2b165245b8e05f7df166df79488438712b1f7ee6" } } ], "extra": [ 1, 73, 26, 196, 182, 132, 213, 88, 215, 76, 67, 182, 101, 164, 71, 116, 24, 76, 95, 253, 45, 213, 179, 211, 1, 142, 78, 196, 165, 64, 173, 121, 7, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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