Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec2eb37321984c8f7872bd9a0eaeeb9ac5b1d334d2f1fe9006f9e34380cbbb6a

Tx prefix hash: 426832195371fb309d040a078451246bf4b87dbe3367df01092590b90a2e0e74
Tx public key: c976e8468aacadfafeb23d0b2ce810f4a0193a58817ac709058e619f37b03904
Timestamp: 1727458442 Timestamp [UCT]: 2024-09-27 17:34:02 Age [y:d:h:m:s]: 00:057:10:12:38
Block: 1119389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41040 RingCT/type: yes/0
Extra: 01c976e8468aacadfafeb23d0b2ce810f4a0193a58817ac709058e619f37b0390402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d15b12136b244c8fa938aa9d5d0b1690ed040197d815051193b767cf75cc61a 0.600000000000 1600928 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": 1119399, "vin": [ { "gen": { "height": 1119389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d15b12136b244c8fa938aa9d5d0b1690ed040197d815051193b767cf75cc61a" } } ], "extra": [ 1, 201, 118, 232, 70, 138, 172, 173, 250, 254, 178, 61, 11, 44, 232, 16, 244, 160, 25, 58, 88, 129, 122, 199, 9, 5, 142, 97, 159, 55, 176, 57, 4, 2, 17, 0, 0, 0, 2, 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