Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38b49b861d0dbd83b4cad4b9fbc2ebce404527e87c704d1c2e8ea326ef938d3b

Tx prefix hash: 9b5c400c6a55ae1ce484ef7a6074641d0ef42faebb2ff6eae74f9df833daa938
Tx public key: 506e4f16b2cba6b87684c476686452002235bf9dea53357704dae4410a7786e8
Timestamp: 1705482043 Timestamp [UCT]: 2024-01-17 09:00:43 Age [y:d:h:m:s]: 01:099:09:41:37
Block: 937177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332159 RingCT/type: yes/0
Extra: 01506e4f16b2cba6b87684c476686452002235bf9dea53357704dae4410a7786e802110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6ae6ce0895d0ca3aaf3632e632ad7a56b7c1b559cd3d33d518f61f9b78480e3 0.600000000000 1395221 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": 937187, "vin": [ { "gen": { "height": 937177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6ae6ce0895d0ca3aaf3632e632ad7a56b7c1b559cd3d33d518f61f9b78480e3" } } ], "extra": [ 1, 80, 110, 79, 22, 178, 203, 166, 184, 118, 132, 196, 118, 104, 100, 82, 0, 34, 53, 191, 157, 234, 83, 53, 119, 4, 218, 228, 65, 10, 119, 134, 232, 2, 17, 0, 0, 0, 7, 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