Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f94464fdba81ef0faeb38869e34eaf035d24e35b16a19a319a0ec79b00f2543a

Tx prefix hash: d57b75d5dd6eb7f025478be1d5f093da4ed4bdaf3e97cca71c7a5d08c3fe5498
Tx public key: 91ddb7a94588bc964321726e2dee17b059f789e55bb0cb2bbf81de8866db6a06
Timestamp: 1728752738 Timestamp [UCT]: 2024-10-12 17:05:38 Age [y:d:h:m:s]: 00:187:10:23:56
Block: 1130117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133752 RingCT/type: yes/0
Extra: 0191ddb7a94588bc964321726e2dee17b059f789e55bb0cb2bbf81de8866db6a0602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b70d33b411c2e8b8a79c090ad370df6bf6ed6e3488ecf135219af05114b0546 0.600000000000 1612990 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": 1130127, "vin": [ { "gen": { "height": 1130117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b70d33b411c2e8b8a79c090ad370df6bf6ed6e3488ecf135219af05114b0546" } } ], "extra": [ 1, 145, 221, 183, 169, 69, 136, 188, 150, 67, 33, 114, 110, 45, 238, 23, 176, 89, 247, 137, 229, 91, 176, 203, 43, 191, 129, 222, 136, 102, 219, 106, 6, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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