Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e46341328b58c9623a49dbe6c6b6cd8a3a1128465cc7e2b39f9aa1ec7025388c

Tx prefix hash: 0014f4c648a85634bf8d6dacad7622cef22f35889a35d8445ca07651c2cffaf0
Tx public key: 3965a6fa6ed3a6d626b3258151bb376472b4ae339d5a225a206b19664cb4bace
Timestamp: 1725722243 Timestamp [UCT]: 2024-09-07 15:17:23 Age [y:d:h:m:s]: 00:234:17:11:05
Block: 1105005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167612 RingCT/type: yes/0
Extra: 013965a6fa6ed3a6d626b3258151bb376472b4ae339d5a225a206b19664cb4bace021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a93836b7b2bfd7099a94b6b374683c1e8d022a4ae81c528a84e747af43c16b3 0.600000000000 1582340 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": 1105015, "vin": [ { "gen": { "height": 1105005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a93836b7b2bfd7099a94b6b374683c1e8d022a4ae81c528a84e747af43c16b3" } } ], "extra": [ 1, 57, 101, 166, 250, 110, 211, 166, 214, 38, 179, 37, 129, 81, 187, 55, 100, 114, 180, 174, 51, 157, 90, 34, 90, 32, 107, 25, 102, 76, 180, 186, 206, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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