Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f317a3d3c8ae0ef32265b4f610ca7143fd145472c549d79b3ccdb1e955641117

Tx prefix hash: 980cd5a9e2fbd0e370a4ec8499a79a260aac6f3be10bb477d616461feed3a9ba
Tx public key: 0db786faceb3a90f6b51ce4a97b277c8fdffc063d1414c2c22348739b2357c9f
Timestamp: 1717291546 Timestamp [UCT]: 2024-06-02 01:25:46 Age [y:d:h:m:s]: 00:304:00:20:00
Block: 1035104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217257 RingCT/type: yes/0
Extra: 010db786faceb3a90f6b51ce4a97b277c8fdffc063d1414c2c22348739b2357c9f021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 910ee1a3fc21c65c3f298c0cb72d7115caee964d41579dd891969e14874de9e1 0.600000000000 1503623 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": 1035114, "vin": [ { "gen": { "height": 1035104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "910ee1a3fc21c65c3f298c0cb72d7115caee964d41579dd891969e14874de9e1" } } ], "extra": [ 1, 13, 183, 134, 250, 206, 179, 169, 15, 107, 81, 206, 74, 151, 178, 119, 200, 253, 255, 192, 99, 209, 65, 76, 44, 34, 52, 135, 57, 178, 53, 124, 159, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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