Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48a88e508b02fe4794dc6ce60b5b7f303776b912512efc9e6e4174aa9f995656

Tx prefix hash: 8a86ed0d2569f1f966e2a5b0a4f5c835ceb8e2fa20c839db84aaabc73def3ba1
Tx public key: e84a5c141988fbce43aceac6bae6b7391e75137abf4277a72c53437f34386fe5
Timestamp: 1704729219 Timestamp [UCT]: 2024-01-08 15:53:39 Age [y:d:h:m:s]: 01:094:09:55:12
Block: 930940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328592 RingCT/type: yes/0
Extra: 01e84a5c141988fbce43aceac6bae6b7391e75137abf4277a72c53437f34386fe50211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcf64f958727a8cf31f53b3d5ca7674d0742b054aca3b4bece83e35dddc24416 0.600000000000 1388830 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": 930950, "vin": [ { "gen": { "height": 930940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcf64f958727a8cf31f53b3d5ca7674d0742b054aca3b4bece83e35dddc24416" } } ], "extra": [ 1, 232, 74, 92, 20, 25, 136, 251, 206, 67, 172, 234, 198, 186, 230, 183, 57, 30, 117, 19, 122, 191, 66, 119, 167, 44, 83, 67, 127, 52, 56, 111, 229, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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