Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f57327bf242bbcb1dcc6d82eb22e0a5a75e13ccf7afd1dbd017c6c3ca3300e16

Tx prefix hash: d9e7a33c8d705577405b0314ab8b0e31ff97913e057135f0ae2b3658aad13b5f
Tx public key: b3d9363fa87d51805cebce4f71f3e9068b1f0baa00c00270b969d18305f1bd2f
Timestamp: 1703657063 Timestamp [UCT]: 2023-12-27 06:04:23 Age [y:d:h:m:s]: 01:134:17:28:51
Block: 922056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357434 RingCT/type: yes/0
Extra: 01b3d9363fa87d51805cebce4f71f3e9068b1f0baa00c00270b969d18305f1bd2f02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31435a10309e8817da82bf7d7eeeb3f3e9ca9b68f22fbcfe753b83ba72754359 0.600000000000 1379750 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": 922066, "vin": [ { "gen": { "height": 922056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31435a10309e8817da82bf7d7eeeb3f3e9ca9b68f22fbcfe753b83ba72754359" } } ], "extra": [ 1, 179, 217, 54, 63, 168, 125, 81, 128, 92, 235, 206, 79, 113, 243, 233, 6, 139, 31, 11, 170, 0, 192, 2, 112, 185, 105, 209, 131, 5, 241, 189, 47, 2, 17, 0, 0, 0, 6, 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