Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e6f1f6b3c3c54f25ba3b66590e0df5436a5a64836d598603aa0c7544a9ea51b

Tx prefix hash: 6d1ad878b278eb1c8b10ab5d40d1d46b3426229c91e00536335fe99fff271972
Tx public key: ae8d21156917faf33772288677c2f1180414a517f106e2274446806b99e8c251
Timestamp: 1581266736 Timestamp [UCT]: 2020-02-09 16:45:36 Age [y:d:h:m:s]: 04:321:15:38:39
Block: 61593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121873 RingCT/type: yes/0
Extra: 01ae8d21156917faf33772288677c2f1180414a517f106e2274446806b99e8c2510211000000094943cd9f000000000000000000

1 output(s) for total of 383.651554499000 dcy

stealth address amount amount idx
00: 378cf5a4c785e8f982ec60e8dd46aa3075cf90e78608e941df68ad542d1c512a 383.651554499000 113526 of 0

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": 61603, "vin": [ { "gen": { "height": 61593 } } ], "vout": [ { "amount": 383651554499, "target": { "key": "378cf5a4c785e8f982ec60e8dd46aa3075cf90e78608e941df68ad542d1c512a" } } ], "extra": [ 1, 174, 141, 33, 21, 105, 23, 250, 243, 55, 114, 40, 134, 119, 194, 241, 24, 4, 20, 165, 23, 241, 6, 226, 39, 68, 70, 128, 107, 153, 232, 194, 81, 2, 17, 0, 0, 0, 9, 73, 67, 205, 159, 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