Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a5b217434dfed971feb3f6dae2b24ea71505c2bd3075cad057e422475767797

Tx prefix hash: 6e2d16f49673fd24ec94264c6c17630cd8503347aae49f0dba1fda48d6664290
Tx public key: 109bea7e9db92c3723ecbc28590b0d9b583e4fd5933dce2548a59c3150682e9c
Timestamp: 1703764536 Timestamp [UCT]: 2023-12-28 11:55:36 Age [y:d:h:m:s]: 01:094:21:43:19
Block: 922957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328926 RingCT/type: yes/0
Extra: 01109bea7e9db92c3723ecbc28590b0d9b583e4fd5933dce2548a59c3150682e9c02110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70afd93505f4c6d4fb87d1f9cc18677e8e4eb487ddd185fddb34544d0b9b5e1f 0.600000000000 1380663 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": 922967, "vin": [ { "gen": { "height": 922957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70afd93505f4c6d4fb87d1f9cc18677e8e4eb487ddd185fddb34544d0b9b5e1f" } } ], "extra": [ 1, 16, 155, 234, 126, 157, 185, 44, 55, 35, 236, 188, 40, 89, 11, 13, 155, 88, 62, 79, 213, 147, 61, 206, 37, 72, 165, 156, 49, 80, 104, 46, 156, 2, 17, 0, 0, 0, 12, 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