Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c5139f90936c53f6e8b3ad936c2cfa366e622cce57f70d16ec04825bf5a22b4

Tx prefix hash: 9bb70ac9f4671a1ef100c86bdd69173eab357eb9552140acbd6d7405888e3b56
Tx public key: 027eefd6939c93d5558794127a5ce2c93b5ef2a7778ecdfb57f02f6e51cbc6fd
Timestamp: 1715924821 Timestamp [UCT]: 2024-05-17 05:47:01 Age [y:d:h:m:s]: 00:304:06:49:40
Block: 1023779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217493 RingCT/type: yes/0
Extra: 01027eefd6939c93d5558794127a5ce2c93b5ef2a7778ecdfb57f02f6e51cbc6fd02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ccd2b6ea1e8297fa69cd48006c8fd11d649af45a536ad37797799868b2f9d9f 0.600000000000 1489006 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": 1023789, "vin": [ { "gen": { "height": 1023779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ccd2b6ea1e8297fa69cd48006c8fd11d649af45a536ad37797799868b2f9d9f" } } ], "extra": [ 1, 2, 126, 239, 214, 147, 156, 147, 213, 85, 135, 148, 18, 122, 92, 226, 201, 59, 94, 242, 167, 119, 142, 205, 251, 87, 240, 47, 110, 81, 203, 198, 253, 2, 17, 0, 0, 0, 4, 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