Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3f5ffb7b1d3782689b8c2bf1c4c9c65a204f4a3ed6c4661b75d0a600e66ed65

Tx prefix hash: 3cbfabafda70eb36cb6dd47375f4e408180b5cd26c149a4b533e445ad543dc9e
Tx public key: 0dc1dfec81b5a583d89471df1e322ee9c9fc50a03b79ccfc8df95aefd392df77
Timestamp: 1713593050 Timestamp [UCT]: 2024-04-20 06:04:10 Age [y:d:h:m:s]: 00:218:21:54:42
Block: 1004415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156725 RingCT/type: yes/0
Extra: 010dc1dfec81b5a583d89471df1e322ee9c9fc50a03b79ccfc8df95aefd392df770211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13eb96c219b5e083b75d374f1b7bb6f16d0294221cacc6aa309ddd433ecb4f1e 0.600000000000 1464983 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": 1004425, "vin": [ { "gen": { "height": 1004415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13eb96c219b5e083b75d374f1b7bb6f16d0294221cacc6aa309ddd433ecb4f1e" } } ], "extra": [ 1, 13, 193, 223, 236, 129, 181, 165, 131, 216, 148, 113, 223, 30, 50, 46, 233, 201, 252, 80, 160, 59, 121, 204, 252, 141, 249, 90, 239, 211, 146, 223, 119, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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